Updating a firmware image using a firmware debugger application

ABSTRACT

Systems, methods, and computer-readable media provide for updating a firmware image during a debugging sequence using a firmware debugger application without re-flashing each updated firmware image on a non-volatile memory device. Embodiments include a debugger application operating on a host computer system and a debugger driver located within a firmware image undergoing the debugging sequence on a target computer system. The debugger application and debugger driver may communicate and transfer data between one another. Upon detecting an error in a firmware image, the debugger driver notifies the debugger application. The debugger application sends an updated firmware image to the debugger driver on the target computer system. The debugger driver loads the updated firmware image and passes control to an entry point of the updated firmware image for continued debugging from the new entry point.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.12/948,500 entitled “Updating a Firmware Image Using a Firmware DebuggerApplication,” filed Nov. 17, 2010, now U.S. Pat. No. 8,135,993, which ishereby incorporated by reference in its entirety. This application alsois a continuation of U.S. patent application Ser. No. 11/952,595entitled “Updating a Firmware Image Using a Firmware DebuggerApplication,” filed Dec. 7, 2007, now U.S. Pat. No. 7,861,119, which ishereby incorporated reference in its entirety.

BACKGROUND

Firmware may be described as software that is embedded within a hardwaredevice. Typically, firmware that includes a basic input/output system(BIOS) for a particular computer hardware configuration is stored or“flashed” onto a read-only memory (ROM) device or other non-volatilememory. Many computer systems utilize a BIOS when powering on in orderto prepare the computer system to recognize and control various deviceswithin the computer system. Because firmware is made up of any number ofdrivers, or modules, that support the specific hardware contained withinthe target computer system in which the firmware will be installed, itmust be created by a BIOS engineer according to the specificconfiguration of the target computer system.

When creating firmware for a target computer system, a BIOS engineerwill create a firmware image, containing all of the desired firmwaremodules corresponding to the target computer system. This firmware imageis then flashed onto a ROM device and installed within the targetcomputer system for testing. When errors are found during testing, a newfirmware image containing any updated firmware modules must be createdand re-flashed onto the ROM device. The ROM device is again placed inthe target computer system and testing can resume. Each time thefirmware needs to be updated, a new firmware image must be created andre-flashed onto the ROM device. This process is time consuming andexpensive.

There are hardware-based devices available that simulate a ROM device.An example of such a device is an in-circuit emulator (ICE). An ICE istypically an adapter card that must be physically connected to themotherboard of the target computer system. While an ICE allows firmwareto be debugged without re-flashing each time an update to the firmwareimage is required, an ICE is an expensive solution that requires areconfiguration of the target computer system through the addition of anadapter card during firmware debugging.

It is with respect to these considerations and others that thedisclosure made herein is provided.

SUMMARY

Systems, methods, and computer-readable media are provided herein forupdating a firmware image using a firmware debugger application.According to one implementation described herein, a method includesestablishing a communications link with a target computer system using adebugger driver within an initial firmware image that is executingduring a debugging sequence on the target computer system. The initialfirmware image includes the debugger driver and multiple firmwaremodules. An error notification associated with one or more problemfirmware modules is received from the debugger driver via thecommunications link.

An updated firmware image that includes one or more firmware modules toreplace the problem firmware modules is received from a basicinput/output system (BIOS) development application. The updated firmwareimage is transmitted to the target computer system via thecommunications link. The debugger application is instructed to load theupdated firmware image into memory of the target computer system and topass control of the initial firmware image to the designated entry pointof the updated firmware image such that the debugging sequence continuesfrom the designated entry point of the updated firmware image.

According to another implementation of the disclosure presented herein,a debugging sequence in a target computer system is initializedutilizing an initial firmware image. The initial firmware image includesa debugger driver and multiple firmware modules. A communication link isestablished with a host computer system via a debugger applicationresiding on the host computer system. An error is detected during thedebugging sequence and the host computer system is notified of the errorvia the communications link. An updated firmware image is received fromthe host computer system via the debugger application. The updatedfirmware image includes one or more firmware modules for replacing theproblem firmware modules. Instructions from the debugger application areexecuted. These instructions include loading the updated firmware imageinto memory of the target computer system and to pass control of theinitial firmware image to a designated entry point of the updatedfirmware image such that the debugging sequence continues from thedesignated entry point of the updated firmware image.

Yet another implementation includes a debugger application and adebugger driver. The debugger application can communicate with adebugger driver to receive an error notification from the debuggerdriver that indicates one or more problem firmware modules within theinitial firmware image. Additionally, the debugger application mayreceive an updated firmware image from a BIOS development applicationthat includes one or more firmware modules for replacing the one or moreproblem firmware modules within the initial firmware image and adesignated entry point. The debugger application can transmit theupdated firmware image to the target computer system via thecommunications link. The debugger application may instruct the debuggerdriver to load the updated firmware image into memory of the targetcomputer system and to pass control of the initial firmware image to thedesignated entry point of the updated firmware image so that thedebugging sequence continues from the designated entry point of theupdated firmware image.

The debugger driver can use the initial firmware image to initiate adebugging sequence in the target computer system. The initial firmwareimage includes a debugger driver and multiple firmware modules. Thedebugger may establish a communications link with the debuggerapplication of the host computer system. During the debugging sequence,the debugger driver can detect an error associated with one or moreproblem firmware modules and notify the host computer system. Thedebugger driver can receive an updated firmware image from the hostcomputer system via the debugger application and execute instructionsreceived from the debugger application to load the updated firmwareimage into the memory of the target computer system and to pass controlof the initial firmware image to the designated entry point of theupdated firmware image such that the debugging sequence continues fromthe designated entry point of the updated firmware image.

The above-described subject matter may also be implemented as acomputer-controlled apparatus, a computer process, a computing system,or as an article of manufacture such as a computer-readable medium.These and various other features will be apparent from a reading of thefollowing Detailed Description and a review of the associated drawings.

This Summary is provided to introduce a selection of concepts in asimplified form that are further described below in the DetailedDescription. This Summary is not intended to identify key features oressential features of the claimed subject matter, nor is it intended tobe used to limit the scope of the claimed subject matter. Furthermore,the claimed subject matter is not limited to implementations that solveany or all disadvantages noted in any part of this disclosure.

BRIEF DESCRIPTION OF THE DRAWINGS

FIGS. 1-3 are block diagrams showing an illustrative operatingenvironment for the processes and computer systems described herein,including several of the software components utilized by the computersystems described herein, and a process flow for updating a firmwareimage according to one embodiment presented herein;

FIGS. 4A and 4B are flow diagrams showing aspects of the operation of atarget computer system and a host computer system provided in oneimplementation described herein; and

FIG. 5 is a computer architecture diagram showing a computerarchitecture suitable for implementing the various computer systemsdescribed herein.

DETAILED DESCRIPTION

The following detailed description is directed to systems, methods, andcomputer-readable media for updating a firmware image using a firmwaredebugger application. While the subject matter described herein ispresented in the general context of program modules that execute inconjunction with the execution of an operating system and applicationprograms on a computer system, those skilled in the art will recognizethat other implementations may be performed in combination with othertypes of program modules.

Generally, program modules include routines, programs, components, datastructures, and other types of structures that perform particular tasksor implement particular abstract data types. Moreover, those skilled inthe art will appreciate that the subject matter described herein may bepracticed with other computer system configurations, including hand-helddevices, multiprocessor systems, microprocessor-based or programmableconsumer electronics, minicomputers, mainframe computers, and the like.

The subject matter described herein may be practiced in a distributedcomputing environment where tasks are performed by remote processingdevices that are linked through a communications network and whereinprogram modules may be located in both local and remote memory storagedevices. It should be appreciated, however, that the implementationsdescribed herein may also be utilized in conjunction with stand-alonecomputer systems and other types of computing devices. It should also beappreciated that the embodiments presented herein may be utilized withany type of local area network (LAN) or wide area network (WAN).

As stated briefly above, updating a firmware image during debugging istypically a time consuming process since the firmware image often mustbe flashed into non-volatile memory multiple, and often numerous, timesbefore the debugging process is complete. Implementations of thedisclosure provided herein provide for updating a firmware image using afirmware debugger application without the need to physically flashupdated firmware images into a ROM device or other non-volatile memory.According to various embodiments, a debugger application residing on ahost computer system communicates with a debugger driver located withina firmware image undergoing a debugging process on a target computersystem.

Through this communications link, a BIOS engineer can transmit updatedfirmware images, or individual firmware modules, to the target computersystem. The debugger driver can receive an updated firmware image fromthe host computer system and pass control to the entry point of theupdated firmware image to allow the debugging process to continue usingthe updated firmware image. This process may be repeated to update thefirmware image within the RAM of the target computer system without thenecessity of flashing an updated firmware image on a ROM device eachtime a firmware image update is required. This process eliminates theadditional expense associated with hardware solutions to the firmwaredebugging issue. Moreover, by updating the firmware image in RAM insteadof ROM, not only is the updating process faster, it is also possible toutilize firmware images that are larger in size than the ROM device iscapable of storing. Often, a debug version of the firmware image may belarger than the release version will ultimately be. By allowing updatesto a firmware image to occur in RAM, size conflicts with the ROM devicemay be avoided.

In the following detailed description, references are made to theaccompanying drawings that form a part hereof, and which are shown byway of illustration specific embodiments or examples. Referring now tothe drawings, in which like numerals represent like elements through theseveral figures, aspects of a computing system and methodology forupdating a firmware image using a firmware debugger application will bedescribed. FIG. 1 shows a firmware debugging system 100 that is preparedto begin debugging a firmware image 110. FIGS. 2 and 3 will illustratevarious components of the firmware debugging system 100 and actionstaken by those components during a debugging procedure according toimplementations of the disclosure presented herein.

Looking at FIG. 1, the firmware debugging system 100 includes a targetcomputer system 102 and a host computer system 104. The target computersystem 102 includes hardware 106. It should be appreciated that thehardware 106 may include any number and type of computer hardwaredevices, including memory 108. As will be described below with respectto FIG. 5, the memory 108 may include either random access memory (RAM)or ROM or both. For the purposes of the example debugging and firmwareupdating process described below with respect to FIGS. 2 and 3, thememory 108 may be RAM. However, it should be appreciated that thedisclosure presented herein allows for a firmware image to be updated inrandom access memory (RAM) or flash memory.

The target computer system 102 further includes the firmware image 110.The firmware image 110 is the initial firmware image that is configuredfor the target computer system 102 and is being tested and debugged onthe target computer system 102. It should be appreciated that thefirmware image 110 may be initially flashed onto a ROM device andinstalled within the target computer system 102. Using the disclosurepresented herein, a firmware image may be updated and tested numeroustimes without requiring a re-flash of the updated firmware image onto aROM device each time an updated firmware image is created. It shouldalso be appreciated that the firmware image 110 may alternatively bestored and executed from any other installed or removable non-volatilememory device within the target computer system 102 or may have beentransmitted to the target computer system 102 by the host computersystem 104 and stored on the target computer system 102 for executionand debugging.

The firmware image 110 includes a boot block portion 112 and a mainfirmware image portion 114. When the target computer system 102 ispowered on, code within the boot block portion 112 of the firmware image110 executes from the ROM device containing the firmware image 110. Thecode within the boot block portion 112 of the firmware image 110 enablesthe central processing unit (CPU) of the target computer system 102 andinitializes the memory 108 prior to copying the main firmware imageportion 114 to the memory 108. The main firmware image portion 114 isexecuted from the memory 108 rather than from the ROM device. The mainfirmware image portion 114 includes drivers 116A-116N. These drivers116A-116N, or firmware modules, are used by the operating system of thetarget computer system 102 to control the hardware 106. It should beappreciated that the main firmware image portion 114 may include anyquantity and type of drivers 116A-116N depending upon the hardwareconfiguration of the target computer system 102.

According to one implementation of the disclosure presented herein, thefirmware image 110 includes a debugger driver 118. The debugger driver118 is used to locate errors within the firmware image 110 duringtesting. The debugger driver 118 contains code that allows forcommunication, control, and data transfer between the debugger driver118 and a debugger application 120 located on the host computer system104. The debugger driver 118 is loaded into the memory 108 of the targetcomputer system 102 at an early stage in the debugging process to enablea BIOS engineer to control the firmware image testing and debuggingprocess within the target computer system 102 from the host computersystem 104. It should be understood that the debugger driver 118 may belocated in the boot block portion 112 or the main firmware image portion114 of the firmware image 110, or both.

The host computer system 104 includes the debugger application 120 and aBIOS development system 122. The BIOS development system 122 may includeany software or hardware used by a BIOS engineer to create a firmwareimage 110 and subsequent firmware. It should be understood that the BIOSdevelopment system 122 may include the debugger application 120 or maybe separate from and in communication with the debugger application 120.In prior firmware debugging systems, a BIOS engineer would use the BIOSdevelopment system 122 to create the firmware image 110, flash thefirmware image 110 onto a ROM device, install the ROM device within thetarget computer system 102, and repeat the process each time an errorduring the debugging process required an updated firmware image.However, utilizing the implementations described below, updated firmwareimages may be electronically transmitted to the target computer system102, installed, and executed using a communications link between thedebugger application 120 within the host computer system 104 and thedebugger driver 118 within the target computer system 102. Thecommunications link may be physically enabled using a cable 124. Itshould be understood that the cable 124 may be a serial cable or auniversal serial bus (USB) debugging cable.

Turning now to FIG. 2, a block diagram of the firmware debugging system100 shows actions taken by various components of the firmware debuggingsystem 100 upon initiating a debugging sequence. The actions to bediscussed are shown with arrows and corresponding circled numbers. Itshould be understood that implementations of the disclosure presentedherein are not limited to the actions shown or the order in which theactions are discussed or numbered. According to one embodiment, thedebugging sequence begins with the execution of the code within the bootblock portion 112. Action 1 shows the initialization of the memory 108by the boot block portion 112 of the firmware image 110 undergoing thetesting and debugging sequence. Once initialized, action 2 shows thecopying of the main firmware image portion 114 of the firmware image 110being copied to the memory 108.

Communication is established between the debugger driver 118 and thedebugger application 120 of the target computer system 102 and the hostcomputer system 104, respectively, at action 3. As discussed above, thiscommunication is enabled using the serial or USB debugging cable 124.Once the main firmware image portion 114 has been copied to the memory108, then control is passed to the entry point 202 of the main firmwareimage portion 114 in the memory 108 at action 4. This action may includepassing a call to the entry point 202 such that the debugging sequencecontinues from the entry point 202 of the main firmware image portion114 that has been copied into the memory 108, rather than from the mainfirmware image portion 114 of the firmware image 110 that is located onthe ROM device. It should be appreciated that executing the mainfirmware image portion 114 from the memory 108 rather than from the ROMdevice significantly increases the speed of the firmware executionprocess and allows for sufficient memory capacity to enable data to betransferred from the host computer system 104 to the target computersystem 102 using the communication link between the debugger driver 118and the debugger application 120.

FIG. 3 is a block diagram of the firmware debugging system 100 showingactions taken by various components of the firmware debugging system 100after errors in the firmware image 110 have been located. Afterdiscovering an error within the firmware image 110, a BIOS engineer willutilize the BIOS development system 122 to create an updated firmwareimage 310. It should be understood that the updated firmware image 310may include an entire updated main firmware image portion 314, if theerror requiring correction was located in the main firmware imageportion 114 of the firmware image 110, or may include only those drivers316A-316N in which one or more errors were detected. For example, if anerror requiring correction was located in the driver 116A, then theupdated firmware image 310 may include the entire updated main firmwareimage portion 314, which includes drivers 316A-316N, or the updatedfirmware image 310 may include only the driver 316A.

The updated firmware image 310 is received by the debugger application120 at action 1. The debugger application 120 transmits the updatedfirmware image 310 to the debugger driver 118 within the memory 108 ofthe target computer system 102 via the cable 124 at action 2. With theupdated firmware image 310, the debugger application 120 sendsinstructions to the debugger driver 118 to pass control to the entrypoint 302 associated with the updated firmware image 310. Theseinstructions are complied with at actions 3 and 4, respectively. Afterpassing control to the new entry point 302, the debugging sequencecontinues from that entry point, utilizing the drivers 316A-316N withinthe updated firmware image 310 rather than the drivers 116A-116N of theoriginal firmware image 110. This process repeats for each error thatrequires correction.

In this manner, the BIOS engineer is able to save considerable timeduring debugging the firmware image 110 since the updated firmwareimages 310 are transmitted to the target computer system 102electronically rather than requiring manual flashing of each updatedfirmware image 310 onto a ROM device and installing the ROM device intothe target computer system 102. After the debugging sequence iscomplete, the BIOS development system 122 is used to create a finalfirmware image from all of the applicable error-free firmware modules,which is then flashed onto a ROM device to create the target firmware312 for the target computer system 102. This debugging and firmwareupdating sequence will be described in greater detail below with respectto FIGS. 4A and 4B.

Turning now to FIGS. 4A and 4B, additional details will be providedregarding the operation of the target computer system 102 and the hostcomputer system 104. In particular, FIGS. 4A and 4B are flow diagramsshowing a routine 400 that illustrates aspects of the operation of thetarget computer system 102 and a routine 450 that illustrates aspects ofthe operation of the host computer system 104 for updating a firmwareimage using a firmware debugger application according to variousembodiments presented herein. It should be appreciated that the logicaloperations described herein with respect to FIGS. 4A and 4B areimplemented (1) as a sequence of computer implemented acts or programmodules running on a computing system and/or (2) as interconnectedmachine logic circuits or circuit modules within the computing system.The implementation is a matter of choice dependent on the performancerequirements of the computing system. Accordingly, the logicaloperations described herein are referred to variously as operations,structural devices, acts, or modules. These operations, structuraldevices, acts and modules may be implemented in software, in firmware,in special purpose digital logic, and any combination thereof. It shouldalso be appreciated that more or fewer operations may be performed thanshown in FIGS. 4A and 4B and described herein. These operations may alsobe performed in a different order than those described herein withrespect to FIGS. 4A and 4B.

The routine 400 begins at operation 402, where the target computersystem 102 initiates the debugging sequence. As described above, thedebugging sequence begins with the boot block portion 112 of thefirmware image 110 executing code to initialize the memory 108 and copythe main firmware image portion 114 of the firmware image 110 into thememory 108. From operation 402, the routine 400 continues to operation404, where the debugger driver 118 is loaded into the memory 108. Thismay occur when the main firmware image portion 114 is copied into thememory 108. The routine 400 continues from operation 404 to operation406, where the debugger driver 118 establishes communication with thedebugger application 120 within the host computer system 104. Routine450, illustrating aspects of the operation of the host computer system104, begins at operation 452 by establishing the communication link withthe debugger driver 118. From operation 452, the routine 450 continuesto operation 454 and proceeds as described below.

Returning to the routine 400, from operation 406, the routine 400continues to operation 408, where the debugger driver 118 determineswhether an error has occurred during the execution of the firmware image110. If an error has not been detected at operation 408, the routine 400proceeds to operation 410 where a determination is made as to whetherthe debugging sequence has completed. The debugging sequence hascompleted when all of the drivers 116A-116N have been executed, allowingthe operating system of the target computer system 102 to successfullytake control of all of the hardware 106 associated with the targetcomputer system 102. If the debugging sequence has completed, whichcorresponds to an error-free firmware image 110, then the routine 400continues to operation 414 and ends. However, if at operation 410 it isdetermined that the debugging sequence has not completed, then theroutine 400 returns to operation 408 and proceeds as described above.

At operation 408, if the debugger driver 118 detects an error in thedebugging sequence, then the routine 400 continues to operation 412,where the debugger driver 118 notifies the debugger application 120 ofthe error via the established communications link. The debuggerapplication 120 of the host computer system 104 receives thenotification at operation 454 of routine 450. From operation 454, theroutine 450 continues to operation 456, where the debugger application120 presents the BIOS engineer or other user with the applicable detailsof the error. The BIOS engineer then creates an updated firmware image310 using the BIOS development system 122. The routine 450 continues tooperation 458, where the debugger application 120 receives the updatedfirmware image 310 from the BIOS development system. From operation 458,the routine 450 continues to operation 460, where the debuggerapplication 120 sends the updated firmware image 310 to the targetcomputer system 102 with instructions to load the updated firmware image310 into the memory 108 of the target computer system 102 and to passcontrol to the entry point 302 of the updated firmware image 310. Aftersending the updated firmware image 310 to the target computer system102, the routine 450 continues to operation 462 and ends.

At operation 416 of the routine 400, the debugger driver 118 receivesthe updated firmware image 310. As discussed above, the updated firmwareimage 310 may include an updated main firmware image portion 314, or mayinclude one or more drivers 316A-316N to replace one or more drivers116A-116N of the firmware image 110 that contain errors. From operation416, the routine 400 continues to operation 418, where the debuggerdriver 118 loads the updated firmware image 310 into the memory 108. Theroutine continues from operation 418 to operation 420, where thedebugger driver 118 passes control to the entry point 302 of the updatedfirmware image 310 so that the debugging sequence continues from theentry point 302 of the updated firmware image 310 rather than from anypoint in the firmware image 110, which contains one or more errors. Fromoperation 420, the routine 400 returns to operation 408 and continues asdescribed above. It should be understood that once the debuggingsequence illustrated by routines 400 and 450 have completed, the BIOSengineer may create a target firmware 312 from the error-free modules ofthe firmware image 110 and any updated firmware image 310.

Referring now to FIG. 5, an illustrative computer architecture for acomputer 500 utilized in the various embodiments presented herein willbe discussed. The computer architecture shown in FIG. 5 illustrates aconventional desktop, laptop computer, or server computer. The computerarchitecture shown in FIG. 5 includes a CPU 502, a system memory 508,including a RAM 514 and a ROM 516, and a system bus 504 that couples thememory to the CPU 502. A BIOS containing the basic routines that help totransfer information between elements within the computer 500, such asduring startup, is stored in the ROM 516. The computer 500 furtherincludes a mass storage device 510 for storing an operating system 518,application programs, and other program modules, which will be describedin greater detail below.

The mass storage device 510 is connected to the CPU 502 through a massstorage controller (not shown) connected to the bus 504. The massstorage device 510 and its associated computer-readable media providenon-volatile storage for the computer 500. Although the description ofcomputer-readable media contained herein refers to a mass storagedevice, such as a hard disk or CD-ROM drive, it should be appreciated bythose skilled in the art that computer-readable media can be anyavailable media that can be accessed by the computer 500.

By way of example, and not limitation, computer-readable media mayinclude volatile and non-volatile, removable and non-removable mediaimplemented in any method or technology for storage of information suchas computer-readable instructions, data structures, program modules orother data. For example, computer-readable media includes, but is notlimited to, RAM, ROM, EPROM, EEPROM, flash memory or other solid statememory technology, CD-ROM, digital versatile disks (DVD), HD-DVD,BLU-RAY, or other optical storage, magnetic cassettes, magnetic tape,magnetic disk storage or other magnetic storage devices, or any othermedium which can be used to store the desired information and which canbe accessed by the computer 500.

According to various embodiments, the computer 500 may operate in anetworked environment using logical connections to remote computersthrough a network 501, such as the Internet. The computer 500 mayconnect to the network 501 through a network interface unit 506connected to the bus 504. It should be appreciated that the networkinterface unit 506 may also be utilized to connect to other types ofnetworks and remote computer systems. As described above, the hostcomputer system 104 and the target computer system 102 communicate via aserial or USB debugging cable 124 according to various embodimentsdescribed herein. The computer 500 may also include an input/outputcontroller 512 for receiving and processing input from a number of otherdevices, including a keyboard, mouse, or electronic stylus (not shown inFIG. 5). Similarly, an input/output controller may provide output to adisplay screen, a printer, or other type of output device (also notshown in FIG. 5).

As mentioned briefly above, a number of program modules and data filesmay be stored and executed using the mass storage device 510 and RAM 514of the computer 500, including an operating system 518 suitable forcontrolling the operation of a networked desktop or server computer,such as the WINDOWS XP or WINDOWS VISTA operating systems from MICROSOFTCORPORATION of Redmond, Wash. Other operating systems, such as the LINUXoperating system or the OSX operating system from APPLE COMPUTER, INC.may be utilized. It should be appreciated that the implementationspresented herein may be embodied using a desktop or laptop computer orany other computing devices or systems or combinations thereof.

The mass storage device 510 and RAM 514 may also store and execute oneor more program modules. In particular, the mass storage device 510 andthe RAM 514 may store a debugger application 120, a firmware image 110containing a debugger driver 118, and the other program modulesdescribed above with respect to FIG. 1. Other program modules may alsobe stored in the mass storage device 510 and utilized by the computer500.

Based on the foregoing, it should be appreciated that systems, methods,and computer-readable media for updating a firmware image using adebugger application are provided herein. Although the subject matterpresented herein has been described in language specific to computerstructural features, methodological acts, and computer readable media,it is to be understood that the invention defined in the appended claimsis not necessarily limited to the specific features, acts, or mediadescribed herein. Rather, the specific features, acts and mediums aredisclosed as example forms of implementing the claims.

The subject matter described above is provided by way of illustrationonly and should not be construed as limiting. Various modifications andchanges may be made to the subject matter described herein withoutfollowing the example embodiments and applications illustrated anddescribed, and without departing from the true spirit and scope of thepresent invention, which is set forth in the following claims.

We claim:
 1. A method of debugging a firmware image, the methodcomprising: establishing a communications link with a target computersystem via a debugger driver within an initial firmware image executingduring a debugging sequence on the target computer system, wherein theinitial firmware image comprises the debugger driver and a plurality offirmware modules; receiving from the debugger driver via thecommunications link an error notification associated with a problemfirmware module within the initial firmware image executing during thedebugging sequence; receiving an updated firmware image from a basicinput/output system (BIOS) development system, the updated firmwareimage comprising a replacement firmware module for replacing the problemfirmware module within the initial firmware image and a designated entrypoint; transmitting the updated firmware image to the target computersystem via the communications link; instructing the debugger driver toload the updated firmware image into memory of the target computersystem and to pass control of the initial firmware image to thedesignated entry point of the updated firmware image such that thedebugging sequence continues from the designated entry point of theupdated firmware image; and storing an error-free module from at leastone of the initial firmware image or the updated firmware image tocreate a firmware for the target computer system.
 2. The method of claim1, wherein the initial firmware image comprises a boot block portion anda main firmware image portion and wherein the debugger driver is locatedwithin the main firmware image portion.
 3. The method of claim 1,wherein the initial firmware image comprises a boot block portion and amain firmware image portion and wherein the updated firmware imagecomprises a main firmware image portion.
 4. The method of claim 1,wherein the updated firmware image comprises a single firmware module.5. The method of claim 1, wherein receiving the error notification,receiving the updated firmware image from the BIOS development system,transmitting the updated firmware image to the target computer system,and instructing the debugger driver to load the updated firmware imageand pass control to the designated entry point occurs a plurality oftimes, each time corresponding to a problem firmware module within theinitial firmware image or an updated firmware image.
 6. The method ofclaim 1, wherein the error-free module is stored in a non-volatilememory.
 7. The method of claim 1, wherein the communications link isestablished via a universal serial bus (USB) debugger cable.
 8. Themethod of claim 1, further comprising identifying the error-free modulewithin at least one of the initial firmware image or the updatedfirmware image during the debugging sequence.
 9. A method of debugging afirmware image, the method comprising: initiating a debugging sequencein a target computer system utilizing an initial firmware image, whereinthe initial firmware image comprises a debugger driver and a pluralityof firmware modules; establishing a communications link between thetarget computer system and a host computer system; detecting an errorduring the debugging sequence associated with a problem firmware modulewithin the initial firmware image; notifying the host computer system ofthe error via the communications link; receiving, at the target computersystem, an updated firmware image from the host computer system via thedebugger application, the updated firmware image comprising areplacement firmware module for replacing the problem firmware modulewithin the initial firmware image and a designated entry point;executing instructions received from the debugger application to loadthe updated firmware image into memory of the target computer system andto pass control of the initial firmware image to the designated entrypoint of the updated firmware image such that the debugging sequencecontinues from the designated entry point of the updated firmware image;and storing an error-free module from at least one of the initialfirmware image or the updated firmware image to create a firmware forthe target computer system.
 10. The method of claim 9, wherein theinitial firmware image comprises a boot block portion and a mainfirmware image portion and wherein the debugger driver is located withinthe boot block portion.
 11. The method of claim 9, wherein the initialfirmware image comprises a boot block portion and a main firmware imageportion and wherein the updated firmware image comprises a main firmwareimage portion.
 12. The method of claim 9, wherein detecting the error,notifying the host computer system of the error, receiving the updatedfirmware image from the host computer system, and executing theinstructions from the host computer system occurs a plurality of times,each time corresponding to an error associated with a problem firmwaremodule within the initial firmware image or within an updated firmwareimage.
 13. The method of claim 9, wherein the error-free module isstored in a non-volatile memory.
 14. The method of claim 9, furthercomprising computer-executable instructions that, when executed by thecomputer, cause the computer to identify the error-free module within atleast one of the initial firmware image or the updated firmware imageduring the debugging sequence.
 15. A non-transitory computer storagemedium having computer-executable instructions stored thereon that, whenexecuted by a computer, cause the computer to: establish acommunications link with a target computer system via a debugger driverwithin an initial firmware image, wherein the initial firmware imagecomprises the debugger driver and a plurality of firmware modules;receive from the debugger driver an error notification associated with aproblem firmware module within the initial firmware image; receive anupdated firmware image comprising a replacement firmware module forreplacing the problem firmware module within the initial firmware imageand a designated entry point; transmit the updated firmware image to thetarget computer system via the communications link; instruct thedebugger driver to load the updated firmware image into memory of thetarget computer system and to pass control of the initial firmware imageto the designated entry point of the updated firmware image; and storean error-free module from at least one of the initial firmware image orthe updated firmware image to create a firmware for the target computersystem.
 16. The computer storage medium of claim 15, wherein the initialfirmware image comprises a boot block portion and a main firmware imageportion and wherein the debugger driver is located within the mainfirmware image portion.
 17. The computer storage medium of claim 15,wherein the initial firmware image comprises a boot block portion and amain firmware image portion and wherein the updated firmware imagecomprises a main firmware image portion.
 18. The computer storage mediumof claim 15, wherein receiving the error notification, receiving theupdated firmware image from the BIOS development system, transmittingthe updated firmware image to the target computer system, andinstructing the debugger driver to load the updated firmware image andpass control to the designated entry point occurs a plurality of times,each time corresponding to a problem firmware module within the initialfirmware image or an updated firmware image.
 19. The computer storagemedium of claim 15, wherein the error-free modules is stored in anon-volatile memory.
 20. The computer storage medium of claim 15,wherein the communications link is established via a universal serialbus (USB) debugger cable.